From f235d7baefb8e11d7670b6c1d690042ed2eaeffa Mon Sep 17 00:00:00 2001 From: Peter Marheine Date: Mon, 8 Jan 2018 16:31:45 +1100 Subject: [PATCH] Recover caveat about -vv and cleaning First added in 72c924230c3df67261642f74ba415cb34086935f which failed to update the book and was replaced in 1271bb4de0c0e0a085be239c2418af9c673ffc87. --- src/doc/src/reference/build-scripts.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/src/doc/src/reference/build-scripts.md b/src/doc/src/reference/build-scripts.md index aa62140b8..53074238c 100644 --- a/src/doc/src/reference/build-scripts.md +++ b/src/doc/src/reference/build-scripts.md @@ -48,9 +48,13 @@ the source directory of the build script’s package. All the lines printed to stdout by a build script are written to a file like `target/debug/build//output` (the precise location may depend on your configuration). If you would like to see such output directly in your terminal, -invoke cargo as 'very verbose' with the `-vv` flag. Any line that starts with -`cargo:` is interpreted directly by Cargo. This line must be of the form -`cargo:key=value`, like the examples below: +invoke cargo as 'very verbose' with the `-vv` flag. Note that if neither the +build script nor project source files are modified, subsequent calls to +cargo with `-vv` will **not** print output to the terminal because a +new build is not executed. Run `cargo clean` before each cargo invocation +if you want to ensure that output is always displayed on your terminal. +Any line that starts with `cargo:` is interpreted directly by Cargo. +This line must be of the form `cargo:key=value`, like the examples below: ```shell # specially recognized by Cargo -- 2.30.2